Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional settings in Shoes::App #556

Closed
wants to merge 1 commit into from
Closed

Optional settings in Shoes::App #556

wants to merge 1 commit into from

Conversation

noahgibbs
Copy link
Collaborator

Description

Add settings for Shoes::App which will be ignored by the Lacci side.

A Shoes application can be specific to a particular Shoes implementation, and can have settings that are specific to that implementation. A gtk-scarpe application might want to specify a particular GTK+ theme. A scarpe-wasm app might specify how much local storage it wants reserved on its behalf. A SpaceShoes app might want to specify the Ruby version for ruby.wasm or the div to use for displaying output.

For that, we want Lacci to permit (optional) settings that will be passed through to the Scarpe implementation.

Like "features" (a list of symbols and symbol-lists which cannot contain significant data), this is an optional extension to Shoes. Shoes3 did not have this parameter.

Possible future work: should this parameter be gated behind the :scarpe feature?

Checklist

  • Run tests locally

@noahgibbs
Copy link
Collaborator Author

On second thought, I think this isn't a great idea. It's a new Shoes3 incompatibility. There's basically always a way to do the same thing another way (e.g. env vars, or attributes on HTML elements for SpaceShoes.) And the setting values are purely Scarpe-impl-dependent, so it's kind of a liability to even include them.

@noahgibbs noahgibbs closed this Jun 5, 2024
@noahgibbs noahgibbs deleted the lacci-settings branch June 5, 2024 12:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant